- Use a single volume with all disks for true JBOD round-robin
  distribution instead of one volume per disk (which was tiered storage)
- Remove redundant MountPath fallback in storageJbodConfigGenerator.Generate;
  WithDefaults() already guarantees a non-empty value
- Validate duplicate mountPaths across additionalDataVolumeClaimSpecs,
  including implicit defaults colliding with explicit paths

Remove dead ReplicaUpdateInput.DataVolumeClaimSpec field, rename
primaryPVCName to targetPVCName for clarity, always preserve
immutable volumeClaimTemplates on StatefulSet updates, fix potential
panic on empty MountPath, and extract AdditionalDiskBasePath constant.

Truncate the generated version probe Job name prefix so the final name stays within the 63-character Kubernetes label value limit, and add focused unit tests for truncation and non-truncation cases.

Handle additional disk updates for existing ClickHouse clusters by creating per-replica PVCs separately from StatefulSet volumeClaimTemplates, updating pod mounts to use explicit PVC volumes, and allowing additive additionalDataVolumeClaimSpecs updates while blocking remove/rename operations.

ReconcilePVC previously delegated to reconcileResource which replaced the
entire PVC spec, causing API rejections on immutable fields (VolumeName,
VolumeMode, AccessModes, StorageClassName, etc.) for bound PVCs.

Replace with a surgical merge patch that only touches the actually mutable
fields: spec.resources.requests.storage, spec.volumeAttributesClassName,
and labels. StorageClassName divergence is detected and surfaced as a
warning event rather than silently ignored or sent as an invalid update.

…lickHouse compatibility

Disk names used in additionalDataVolumeClaimSpecs serve dual purposes:
as Kubernetes PVC/volume names (requiring lowercase alphanumeric + hyphens)
and as ClickHouse disk identifiers (forbidding hyphens). Previously there
was no format validation, allowing names like disk-backfill-1 to pass
admission but fail in ClickHouse, or names with underscores to pass but
fail Kubernetes PVC creation.

- Add webhook validation enforcing Kubernetes DNS label rules
  (lowercase alphanumeric and hyphens, must start/end with alphanumeric)
- Add matching +kubebuilder:validation:Pattern marker to the CRD type so
  the API server enforces the same constraint even without the webhook
- Regenerate CRD manifests
- Sanitize hyphens → underscores in the ClickHouse JBOD config generator
  so users use Kubernetes-valid names and the operator handles the
  ClickHouse naming requirement transparently